home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Tools (InfoMagic)
/
Internet Tools.iso
/
dos_win
/
winsock
/
maillist
/
93-11.Z
/
93-11
/
000111_news@samba.oit.unc.edu _Mon Nov 29 06:18:58 1993.msg
< prev
next >
Wrap
Internet Message Format
|
1993-11-30
|
7KB
Received: from samba.oit.unc.edu by SunSITE.unc.edu (SMI4.1/FvK 1.02)
id AA11336; Mon, 29 Nov 93 06:18:58 EST
Return-Path: <news>
Received: by samba.oit.unc.edu (5.65/TAS/11-16-88)
id AA00690; Mon, 29 Nov 1993 06:18:37 -0500
Received: from GATEWAY by samba.oit.unc.edu with netnews
for winsock@sunsite.unc.edu (winsock@sunsite.unc.edu)
To: winsock@calypso.oit.unc.edu
Date: Mon, 29 Nov 1993 10:19:13 +0000
From: phil@iisc.demon.co.uk (Philip Shotton)
Message-Id: <PHIL.93Nov29101913@dylan.iisc.demon.co.uk>
Organization: IISC, Brain Surgery Dept.
Sender: ses@calypso.oit.unc.edu
References: <daf10.20.00128203@cwru.edu>
Subject: Re: blocking
In article <daf10.20.00128203@cwru.edu> daf10@cwru.edu (David A. Ferrance) writes:
Can someone tell me about blocking and the WSAE_WOULD_BLOCK (not sure if that
is it exactly-- close though). I have no understanding of these concepts and
although so far it has not hurt me, I'm sure that it will eventually. This is
until I can get home and get a book on the subject...
thanks,
dave
Blocking simply means that a function call will not return until the
operation is completed or terminates due to error. However if a
resource has been set as non-blocking, then a function call that
_would_ block in blocking mode, will return the error
WSAE_WOULD_BLOCK. ie:
n=recv(sock,buff,50,flags)
If sock is a blocking socket, n will either be 50 (and the function
may take some time to return - possibly days!); or possibly return -1
indicating an error. However if sock is flagged as non-blocking, the
same call would return immediately with either 0 < n <= 50 (ie as many
bytes as available to be read), or -1 to indicate error. If the
latter, then the WSAGetLastError() call will return WSAEWOULDBLOCK if
there was no data ready to be read.
Since Windows is brain-dead and can't pre-emptively multi-task, then
all programming should use non-blocking calls, otherwise all other
tasks will be hung waiting for completion.
Phil
--
#### Phil Shotton - phil@iisc.demon.co.uk ####
#### Investment Intelligence Systems Corporation, London, UK ####
#### Phone: +44 (0) 71 628 6960. Fax: +44 (0) 71 638 7528 ####
###! It's life Jim, but not as we know it !###
From news@samba.oit.unc.edu Mon Nov 29 08:39:02 1993
Received: from samba.oit.unc.edu by SunSITE.unc.edu (SMI4.1/FvK 1.02)
id AA17627; Mon, 29 Nov 93 08:39:02 EST
Return-Path: <news>
Received: by samba.oit.unc.edu (5.65/TAS/11-16-88)
id AA05613; Mon, 29 Nov 1993 08:37:13 -0500
Received: from GATEWAY by samba.oit.unc.edu with netnews
for winsock@sunsite.unc.edu (winsock@sunsite.unc.edu)
To: winsock@calypso.oit.unc.edu
Date: 29 Nov 93 14:27:00 GMT
From: rdri@nki.nl (Richard van Drimmelen)
Message-Id: <1993Nov29.142700.7379@nki.nl>
Sender: ses@calypso.oit.unc.edu
Subject: Unloading packet drivers ??
Is there a switch to unload:
winpkt
odipkt
pktint
Thanks for your answers.
Richard van Drimmelen
Netherlands Cancer Institute, Amsterdam
rdri@nki.nl
From news@samba.oit.unc.edu Mon Nov 29 09:39:19 1993
Received: from samba.oit.unc.edu by SunSITE.unc.edu (SMI4.1/FvK 1.02)
id AA21838; Mon, 29 Nov 93 09:39:19 EST
Return-Path: <news>
Received: by samba.oit.unc.edu (5.65/TAS/11-16-88)
id AA07559; Mon, 29 Nov 1993 09:34:41 -0500
Received: from GATEWAY by samba.oit.unc.edu with netnews
for winsock@sunsite.unc.edu (winsock@sunsite.unc.edu)
To: winsock@calypso.oit.unc.edu
Date: Mon, 29 Nov 1993 14:54:23
From: koehntopp.pad@sni.de (Frank Koehntopp)
Message-Id: <koehntopp.pad.6.000EE823@sni.de>
Organization: Siemens Nixdorf Informationssysteme AG
Sender: ses@calypso.oit.unc.edu
Subject: VxDTCP site
By popular demand...
gopher biochemistry.cwru.edu
FTP archives/somewhere obviuos... :-)
Will the first to successfully configure NNTP please tell me how he/she did it?
Ta.
Frank.
----------------------------------------------------------------------------
Frank K"ohntopp koehntopp.pad@sni.de
Pohlweg 175 or: koehntopp.pad@sni-usa.com
33100 Paderborn
From skeckhardt@mmm.com Mon Nov 29 11:10:13 1993
Received: from pigseye.mmm.com by SunSITE.unc.edu (SMI4.1/FvK 1.02)
id AA00170; Mon, 29 Nov 93 11:10:13 EST
Received: by pigseye.mmm.com (4.1/SMI-4.1)
id AA02835; Mon, 29 Nov 93 10:08:02 CST
Message-Id: <9311291607.AA02787@pigseye.mmm.com>
From: skeckhardt@mmm.com
Subject: LanMan TCP/IP
To: winsock@sunsite.unc.edu
Date: Mon, 29 Nov 93 9:10:17 CST
Mailer: Elm [revision: 70.85]
There has been some discussion of the LanMan TCP/IP and Winsock in this
forum. I have (finally) succeeded in putting it all together. You can
obtain the LanMan client software (for DOS & Win3.1) via anonymous ftp
from ftp.microsoft.com in the Advsys/MSclient/dos/35 or 525 directory.
(The number refers to the size of floppy from which you will install it.)
It is (I'm almost sure) free, but there is a license agreement involved.
Once you have this software installed, you can install the Winsock. This
software is in the Advsys/lanman/sup-ed/winsock directory. It includes
all of the necessary instructions.
All of this is a lot of trouble if you do not have a LanMan server handy;
the TCP/IP is a memory hog and performance isn't great. But if you want
both LanMan and Winsock, it works. I personally prefer Windows NT or, at
least Win for Workgroups. We can't wait to see if Chicago will be approved
by our Info Tech group and become the corporate standard when it is released.
(Or, more likely, a year later.)
Steve E.
From news@samba.oit.unc.edu Mon Nov 29 12:20:26 1993
Received: from samba.oit.unc.edu by SunSITE.unc.edu (SMI4.1/FvK 1.02)
id AA08219; Mon, 29 Nov 93 12:20:26 EST
Return-Path: <news>
Received: by samba.oit.unc.edu (5.65/TAS/11-16-88)
id AA12786; Mon, 29 Nov 1993 12:08:48 -0500
Received: from GATEWAY by samba.oit.unc.edu with netnews
for winsock@sunsite.unc.edu (winsock@sunsite.unc.edu)
To: winsock@calypso.oit.unc.edu
Date: 29 Nov 1993 16:37:42 GMT
From: heathh@cco.caltech.edu (Heath Ian Hunnicutt)
Message-Id: <2dd8gm$sf4@gap.cco.caltech.edu>
Organization: California Institute of Technology, Pasadena
Sender: ses@calypso.oit.unc.edu
Subject: Announcing: whois for NT
This morning I wrote a whois client for Windows NT (tm). It is just
a command-line client, but it (seems to) work.
You can get the x86 binary from ftp to: ftp.cco.caltech.edu, look
under directory: /pub/heathh/nt/winsock for the files "whois.*"
Don't forget to set mode binary on your ftp client.
Send me mail whether you get it to work or not. I am interested
in whether people find it useful.
Cheers,
Heath
--
--
>From the Home for Amnesiac Computer Scientists....
heathh@cco.caltech.edu